home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980424-19980901
/
000292_news@newsmaster….columbia.edu _Thu Jul 23 14:40:20 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA07047
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 23 Jul 1998 14:40:19 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id OAA08571
for kermit.misc@watsun; Thu, 23 Jul 1998 14:40:19 -0400 (EDT)
Path: news.columbia.edu!panix!howland.erols.net!nntprelay.mathworks.com!news.mathworks.com!uunet!in1.uu.net!news.sonalysts.com!usenet
From: "Michael C. Smith" <mcs@sonalysts.com>
Newsgroups: comp.protocols.kermit.misc
Subject: K95 Server Problem
Date: Thu, 23 Jul 1998 14:30:24 -0400
Organization: Sonalysts, Inc.
Lines: 27
Message-ID: <35B78140.947E2537@sonalysts.com>
NNTP-Posting-Host: sentinel.sonalysts.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.04 [en] (Win95; I)
Xref: news.columbia.edu comp.protocols.kermit.misc:9000
Hi,
I am using Kermit95 to develop an automated file transfer application.
The application is to be used on machines running WindowsNT Server 4.0
(with Service Pack 3). The application sits and waits for incoming
files, currently from a remote dial-in source connecting via PPP/RAS.
Since this is an automated application, we want to cause the Kermit
server to time-out and shut down if a connection to it is idle for more
than a specified langth of time. Under version 1.1.13, the SET SERVER
IDLE-TIMEOUT xxx command worked reasonably well. Under version 1.1.17,
no matter what value we use for the idle-timeout duration, the Kermit
server on the receiving side stays up until it recieves a hangup or
equivalent command to break the connection. The server promptly exits
after such a command and registers if the timeout value was exceded.
Is there some other option that must be set to get this to work in
version 1.1.17? We are currently exploring whether the tcp/ip KeepAlive
settings under NT Server are causing the Kermit server to remain on.
Also, we cannot get the REMOTE LOGIN userID pwd command (issued on the
side sending files to the remote server) to return a failure on an
invalid login attempt. Whether the id /pwd used are accepted by the
remote server or not, the command returns a status of SUCCESS.
Any help with these problems would be greatly appreciated.
Michael C. Smith
<mcs@Sonalysts.com>